feat: publish pipeline#5
Open
darshkpatel wants to merge 2 commits into
Open
Conversation
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Merged
darshkpatel
force-pushed
the
03-17-feat_publish_pipeline
branch
from
March 18, 2025 02:31
79df03e to
1f4e567
Compare
darshkpatel
force-pushed
the
03-17-chore_setup_ci
branch
2 times, most recently
from
March 18, 2025 04:16
e87e20d to
d2156a8
Compare
darshkpatel
force-pushed
the
03-17-feat_publish_pipeline
branch
from
March 18, 2025 04:16
1f4e567 to
77af051
Compare
darshkpatel
force-pushed
the
03-17-chore_setup_ci
branch
from
March 18, 2025 04:41
d2156a8 to
4f96ede
Compare
darshkpatel
force-pushed
the
03-17-feat_publish_pipeline
branch
2 times, most recently
from
March 18, 2025 04:49
024d797 to
706bd93
Compare
darshkpatel
force-pushed
the
03-17-chore_setup_ci
branch
from
March 18, 2025 04:49
4f96ede to
3a55d01
Compare
darshkpatel
force-pushed
the
03-17-feat_publish_pipeline
branch
2 times, most recently
from
March 18, 2025 20:23
1f9ebd8 to
bd207e3
Compare
darshkpatel
force-pushed
the
03-17-chore_setup_ci
branch
from
March 18, 2025 20:31
34a4670 to
fcaca86
Compare
darshkpatel
force-pushed
the
03-17-feat_publish_pipeline
branch
from
March 18, 2025 20:32
bd207e3 to
9f7a049
Compare
darshkpatel
force-pushed
the
03-17-chore_setup_ci
branch
from
March 18, 2025 20:35
fcaca86 to
7f785e6
Compare
darshkpatel
changed the base branch from
03-17-chore_setup_ci
to
graphite-base/5
March 18, 2025 20:35
darshkpatel
force-pushed
the
03-17-feat_publish_pipeline
branch
from
March 18, 2025 20:36
9f7a049 to
dd46f2f
Compare
darshkpatel
force-pushed
the
graphite-base/5
branch
from
March 18, 2025 20:36
fcaca86 to
712cb5d
Compare
darshkpatel
force-pushed
the
03-17-feat_publish_pipeline
branch
from
March 18, 2025 20:36
dd46f2f to
2a202f5
Compare
darshkpatel
marked this pull request as ready for review
March 18, 2025 21:03
darshkpatel
force-pushed
the
03-17-feat_publish_pipeline
branch
from
March 18, 2025 21:08
2a202f5 to
e45ddee
Compare
Collaborator
Author
|
Generated and configured a scoped token 
|
Collaborator
Author
|
Only took 11 months for approval 🥳 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add automated npm package publishing workflow
TL;DR
Add GitHub Actions workflow to automate package publishing and release creation when a new version tag is pushed.
Tested using --dry-run flag
What changed?
.github/workflows/publish.ymlto handle automated package publishingpackage.jsonfor versioning (release:patch,release:minor,release:major)How to test?
Why make this change?
Streamlines the release process by automating the tedious steps of publishing to npm and creating GitHub releases. This ensures consistent releases and reduces manual errors during the publishing process.